Real time event capture, analysis and reporting system

ABSTRACT

Embodiments of the invention are directed to systems, methods, and computer program products for monitoring, identifying and correlating changes to transient event data as a plurality of technology events are processed by a plurality of applications. The proctor module of the system is automatically triggered by addition of event data to transient memory locations associated with the plurality of applications. The proctor module is configured to capture the transient multiple-attribute event data, in real-time, before the data is dequeued. The technology event processing module is configured to format, log and index the captured data from the proctor module. The system then maps an event/record of formatted data associated with a first transient memory location with a second event to another event of formatted data from a second transient memory location, and subsequently analyzes the multi-attribute data to identify changes.

CROSS-REFERENCE TO PRIORITY APPLICATION

This application is a continuation of and claims the benefit of U.S.Non-Provisional patent application Ser. No. 15/288,835 entitled “RealTime Event Capture, Analysis and Reporting System” filed on Oct. 7,2016, which published on Apr. 12, 2018, as U.S. Patent ApplicationPublication No. 2018/0102936, each of which is hereby incorporated byreference in its entirety.

BACKGROUND

Processing of electronic data files typically involves multipleprocessing stages. Systems for high volume data processing requiremultiple applications across various platforms running in order toimplement the processing stages of electronic data. Typically, the eventdata in electronic files is transformed multiple times as technologyprocessing is performed by a plurality of technology platformapplications. This process, however, relies on transient memorylocations to temporarily store the most current transformed event dataafter a processing stage at a particular technology application. Thistransient data is typically unavailable after the subsequent processing.Accordingly, it is difficult to monitor changes that occur to theperpetually altering event data during such processing stages.Therefore, a need exists for novel network architectures that providemonitoring of event data.

BRIEF SUMMARY

The following presents a simplified summary of one or more embodimentsof the invention in order to provide a basic understanding of suchembodiments. This summary is not an extensive overview of allcontemplated embodiments, and is intended to neither identify key orcritical elements of all embodiments, nor delineate the scope of any orall embodiments. Its sole purpose is to present some concepts of one ormore embodiments in a simplified form as a prelude to the more detaileddescription that is presented later.

Embodiments of the present invention comprise systems, methods, andcomputer program products that address these and/or other needs byproviding an innovative system, method and computer program product forreal time event capture and transformation of transient data for aninformation network. The system is configured to enable technology eventdata transformation, processing evaluation and data mapping. Typicallythe system comprises: a plurality of technology platform applicationscomprising an origination platform application and a processing platformapplication, wherein the origination platform application is associatedwith a first transient memory location configured to temporarily storedata until the data is retrieved by the processing platform application,wherein the processing platform application is associated with a secondtransient memory location; a first proctor module application inoperative communication with the first transient memory location,wherein the first proctor module application is configured to capture,in real time, transient data stored in the first transient memorylocation before the data is retrieved by the processing platformapplication; a second proctor module application in operativecommunication with the second transient memory location, wherein thesecond proctor module application is configured to capture, in realtime, transient data stored in the second transient memory location; atleast one memory device with computer-readable program code storedthereon; at least one communication device; at least one processingdevice operatively coupled to the plurality of technology platformapplications, the first proctor module application and the secondproctor module application, the at least one memory device and the atleast one communication device. Executing the computer-readable code isconfigured to cause the at least one processing device to: receive, atthe origination platform application, an origination electronic datafile comprising a plurality of origination technology event recordsregarding processing of a plurality of technology activities, whereineach origination technology event record comprises a plurality oftechnology attributes associated with one of the plurality of technologyactivities; retrieve, by the origination platform application, theplurality of origination technology records from the originationelectronic data file; position, by the origination platform application,a first origination technology event record of the plurality oforigination technology records on a first transient data queue at thefirst transient memory location using an enqueue operation, wherein thefirst transient data queue is configured to temporarily store the firstorigination technology event record until the first originationtechnology event record is retrieved by the processing platformapplication; capture, by the first proctor module application, the firstorigination technology event record, wherein positioning the firstorigination technology event record on the first transient data queue isconfigured to trigger, automatically, the capture of the firstorigination technology event record by the first proctor moduleapplication, wherein capturing further comprises adding the capturedorigination technology event record to a first proctor queue; retrieve,by the processing platform application, the first origination technologyevent record from the first transient data queue at the first transientmemory location using a dequeue operation; process, at the processingplatform application, the first origination technology event record,turning the first origination technology event record to a firstprocessed technology event record; position, by the processing platformapplication, the first processed technology event record on secondtransient data queue at the second transient memory location using anenqueue operation, wherein the second transient data queue is configuredto temporarily store the first processed technology event record;capture, by the second proctor module application, the first processedtechnology event record, wherein positioning the processed technologyevent record on the second transient data queue is configured totrigger, automatically, the capture of the processed technology eventrecord by the second proctor module application, wherein capturingfurther comprises adding the first captured processed technology eventrecord to a second proctor queue; and map, the captured firstorigination technology event record to the captured first processedtechnology event record.

In some embodiments, or in combination with any of the previousembodiments, executing the computer-readable code is configured tofurther cause the at least one processing device to: retrieve, by atechnology data logging application, a plurality of captured eventrecords comprising the captured first origination technology eventrecord and the captured first processed technology event record, fromthe first proctor queue and the second proctor queue; assign, at thetechnology data logging application, a first unique processing eventidentifier to the captured first origination technology event record anda second unique processing event identifier to the captured firstprocessed technology event record; log, by the technology data loggingapplication, the assigned first unique processing event identifier andorigination event metadata comprising a predetermined portion of theplurality of technology attributes associated with the captured firstorigination technology event record, to a first event index memorylocation of an indexing module; and log, by the technology data loggingapplication, the assigned second unique processing event identifier andprocessed event metadata comprising the predetermined portion of theplurality of technology attributes associated with the captured firstprocessed technology event record, to a second event index memorylocation of the indexing module.

In some embodiments, or in combination with any of the previousembodiments, executing the computer-readable code is configured tofurther cause the at least one processing device to: write each of theplurality of the captured technology event records comprising theplurality of technology attributes to a native format event datalocation of an off-disk storage, in native format of the capturedtechnology event record; and wherein the off-disk storage comprises avirtual tape.

In some embodiments, or in combination with any of the previousembodiments, executing the computer-readable code is configured tofurther cause the at least one processing device to transform theplurality of technology attributes associated with each of the pluralityof the captured technology event records to a standard format, using anevent standardization module.

In some embodiments, or in combination with any of the previousembodiments, mapping the captured first origination technology eventrecord to the captured first processed technology event record furthercomprises: determining, for each of the plurality of captured eventrecords comprising the first origination technology event record and thecaptured first processed technology event record, a processing eventtype, wherein the processing event type comprises a origination eventrecord type and a processed event record type; based on determining thatthe captured first origination technology event record is theorigination event record type, assigning a unique activity identifier tothe captured first origination technology event record; based ondetermining that the captured first processing technology event recordis the processed event record type, matching the captured firstprocessed event record to the captured first origination technologyevent record, wherein mapping further comprises assigning the uniqueactivity identifier of the mapped first origination technology eventrecord to the first processed technology event record; and logging, foreach mapped first origination technology event record and firstprocessed technology event record, event metadata and the uniqueactivity identifier associated with the mapped first originationtechnology event record and first processed technology event record to amatching index memory location of an indexing module; wherein the eventmetadata associated with the captured first origination technology eventrecord comprises a predetermined portion of the plurality of technologyattributes of the captured first origination technology event record;wherein the event metadata associated with the captured first processingtechnology event record comprises the predetermined portion of theplurality of technology attributes of the captured first processingtechnology event record.

In some embodiments, or in combination with any of the previousembodiments, wherein executing the computer-readable code is configuredto further cause the at least one processing device to: write each ofthe mapped first origination technology event record and first processedtechnology event record comprising the plurality of technologyattributes to a mapped event data location of an off-disk storage;wherein the off-disk storage comprises a virtual tape.

In some embodiments, or in combination with any of the previousembodiments, the predetermined portion of the plurality of technologyattributes of the captured first origination technology event recordcomprises a predetermined portion of the plurality of technologyattributes that are least likely to be modified during the processing ofthe technology event records by the processing platform application.

In some embodiments, or in combination with any of the previousembodiments, mapping the captured first origination technology eventrecord to the captured first processed technology event record furthercomprises: creating a standardized first origination technology eventrecord by transforming, the plurality of technology attributesassociated with the captured first origination technology event record,to a standard format using an event standardization module; creating astandardized first processed technology event record by transforming,the plurality of technology attributes associated with the capturedfirst processed technology event record, to the standard format usingthe event standardization module; determining, for each of a pluralityof standardized technology event records comprising the standardizedfirst origination technology event record and the standardized firstprocessed technology event record, the event metadata comprising thepredetermined first portion of the plurality of technology attributesthat are least likely to be modified during the processing of thetechnology event records by the processing platform application;determining, for each of the plurality of standardized technology eventrecords, a digital indicator for the event metadata associated with thetechnology event record; and matching the standardized first originationtechnology event record to the standardized first processed technologyevent record based on at least determining that the digital indicator ofthe standardized first origination event record matches the digitalindicator of the standardized first processed event record.

In some embodiments, or in combination with any of the previousembodiments, determining the digital indicator for the event metadatacomprises producing hash values of the event metadata using a hashfunction.

In some embodiments, or in combination with any of the previousembodiments, executing the computer-readable code is configured tofurther cause the at least one processing device to: receive, at adynamic event data evaluation application, a request to determinewhether the first processed technology event record was modified duringthe processing of the first processed technology event record by thefirst processing platform application; retrieve the logged eventmetadata and the unique activity identifier associated with the mappedfirst origination technology event record and processed first technologyevent record, from the matching index memory location of the indexingmodule; retrieve the mapped first origination technology event recordand processed first technology event record from a mapped event datalocation of an off-disk storage, wherein the retrieved event recordscomprises retrieving the plurality of technology attributes associatedwith the with the mapped first origination technology event record andprocessed first technology event record, from the off-disk storage; andcompare each of the technology attributes of the mapped firstorigination technology event record with the attributes of the firstprocessed technology event record to determine any modification totechnology attribute data.

In some embodiments, or in combination with any of the previousembodiments, executing the computer-readable code is configured tofurther cause the at least one processing device to: map, the capturedfirst origination technology event record to the captured firstprocessed technology event record; compare the captured firstorigination technology event record to the captured first processedtechnology event record to identify any modification to the originationtechnology event record; transmit the first processed technology eventrecord to a data integrity checking application of the plurality oftechnology platform applications based on determining that theorigination technology event record has not been modified; initiate theresource transfer activity based on receiving an indication ofsuccessful integrity check of the first processed technology eventrecord, from the data integrity checking application.

Embodiments of the invention are further configured for real time eventcapture and analysis of transient data for an information network. Inthis regard, the invention provides systems, methods and computerprogram products that are configured to enable technology event datatransformation, processing evaluation and data mapping. In someembodiments, or in combination with any of the previous embodiments,executing the computer-readable code is configured to further cause theat least one processing device to: receive, at a charting module, aplurality of captured technology event records, wherein each capturedtechnology event record comprises a plurality of technology attributes,wherein the plurality of captured technology event records comprise aplurality of origination technology event records captured by the firstproctor module from the first transient memory location, and a pluralityof processed technology event records captured by the second proctormodule from the second transient memory location; determine, for each ofthe plurality of captured technology event records, event metadata,wherein the event metadata comprises predetermined portion of theplurality of technology attributes; determine, for a captured firstevent record of the plurality of captured event records, a processingevent type, wherein the processing event type comprises an originationevent record type or a processed event record type, wherein theplurality of origination technology event records are associated withthe origination event record type, wherein the plurality of processedtechnology event records are associated with the processed event recordtype; based on determining that the captured first technology eventrecord is an origination event record type, assigning a unique activityidentifier to the captured first origination technology event record;determine, for a captured second event record of the plurality ofcaptured event records, the processing event type, wherein determiningfurther comprise determining that the captured second technology eventrecord is the processed event record type; matching the captured secondtechnology event record to the captured first technology event record,based on determining that the event metadata of the captured firsttechnology event record matches the event metadata of the capturedsecond technology event record; and assigning the unique activityidentifier of the captured first technology event record to the capturedsecond technology event record.

In some embodiments, or in combination with any of the previousembodiments, executing the computer-readable code is configured tofurther cause the at least one processing device to transform theplurality of technology attributes associated with each of the pluralityof the captured technology event records to a standard format, using anevent standardization module.

In some embodiments, or in combination with any of the previousembodiments, determining that the event metadata of the captured firsttechnology event record matches the event metadata of the capturedsecond technology event record further comprises: transforming, theplurality of technology attributes associated with the captured firsttechnology record and the captured second technology record, to astandard format using an event standardization module; determining, foreach of the captured first technology event and the captured secondtechnology event, a digital indicator for the event metadata associatedwith the technology event record; and matching the captured secondtechnology event record to the captured first technology event recordbased on at least determining that the digital indicator of the capturedfirst technology event record matches the digital indicator of thecaptured second technology event record.

In some embodiments, or in combination with any of the previousembodiments, determining the digital indicator for the event metadatacomprises producing hash values of the event metadata using a hashfunction.

In some embodiments, or in combination with any of the previousembodiments, mapping the captured first technology event record to thecaptured second technology event record further comprises: logging, foreach of the matched first technology event record and second processedtechnology event record, the event metadata and the unique activityidentifier associated with the mapped first technology event record andthe second technology event record to a matching index memory locationof an indexing module.

The features, functions, and advantages that have been discussed may beachieved independently in various embodiments of the present inventionor may be combined with yet other embodiments, further details of whichcan be seen with reference to the following description and drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Having thus described embodiments of the invention in general terms,reference will now be made to the accompanying drawings, wherein:

FIG. 1 depicts a technology event processing system environment 100, inaccordance with one embodiment of the present invention;

FIG. 2 depicts a technology platform module environment 200, inaccordance with one embodiment of the present invention;

FIG. 3 depicts a process map 300 for processing of electronic datafiles, in accordance with one embodiment of the present invention;

FIG. 4 depicts a process map 400 for multi-attribute event datatransformation and processing evaluation, in accordance with oneembodiment of the present invention;

FIG. 5 depicts a high level process flow 500 for mapping of processingevent record with the origination event records, in accordance with oneembodiment of the present invention; and

FIG. 6 depicts a high level process flow 600 for dynamically comparingmulti-attribute record data and evaluating the processing of the data,in accordance with one embodiment of the present invention.

DETAILED DESCRIPTION OF EMBODIMENTS OF THE INVENTION

Systems for high volume data processing require multiple applicationsacross various discrete technology platforms running in order toimplement the processing stages of electronic data. Typically,processing of electronic data files across multiple distributed discretetechnology platforms that are currently used in the large scaleprocessing of electronic files requires a myriad of processes for datatransmission, data reformatting, and substantial transformation oftechnology activity data stored in the electronic files and records.Typically, an electronic file comprising multiple records is processedsequentially by numerous technology applications via discrete technologyprocessing events, with the most current data being transferred from oneapplication to another, via transient memory locations. The data beingtransferred between applications is often transformed or re-formattedmultiple times as a part of the processing itself or to be conductivefor processing by the subsequent technology application and processingplatform. This process, however, relies on transient memory locations tostore the most current transformed event data after a processing eventat a particular technology application. These transient memory locationstypically comprise blocks of memory configured to temporarily store thetransformed event data associated with various processing events ofapplications as they are received. These transient memory locations maybe configured, as in the case of the present invention, to storetransient processing/processed event data in suitable data structuressuch as queues, stacks or linked lists. The current transient data in atransient memory location is overwritten, dequeued, or otherwisedeleted, and as such is unavailable once the data is transferred to thenext technology application for further processing, to allow for eventdata associated with the newer/other files being processed to be storedin these locations.

Typically, the event data in the received electronic files istransformed multiple times as the technology processing is performed bya plurality of technology platform applications. In this regard, thefinal transformed record data often does not resemble the initial recorddata in the received electronic file with respect to the associatedformat, programming language, syntax and/or attributes. Hence,determining whether the underlying data in the transformed record hassubstantially changed is extremely difficult. As such, data alterationsat any of the technology applications, such as processing errors, may bemultiplied/built on by subsequent applications, and may be virtuallyundetectable until the data record is subsequently rejected or is notable to be processed downstream. Accordingly, it is desirable toidentify the various data transformation events and the associatedmodifications to the data to ascertain the stage, type, and technologyapplication associated with such modifications. However, the intricacyof the processing operations via multiple technology applications andplatforms, the sheer volume of electronic files being processed at agiven time and the continual transformation of transient event data thatis only available temporarily at transient memory locations before beingoverwritten, make it very difficult to track the processing ofelectronic files and the associated record data themselves, much lessdetermining the processing of specific records of the files, determiningthe status and content of the data within them at each processingstage/event, and the specific data modification performed by eachtechnology applications. As such, detection of the source of datamodification such as errors, and performing any required corrections isdesirable.

For instance, a data processing system that is configured to processrecords associated with electronic purchase orders may receive about2000 or more order records per minute for real-time processing, from aplurality of external systems. Because these external systems mayoperate on different platforms, operating systems, technical languagesand character sets, the various records received at the data processingsystem may be different from one another in their structure, format,syntax, technical language, character sets and other aspects, such asXML (Extensible Markup Language) format, EBCDIC (Extended Binary CodedDecimal Interchange Code) format, and the like. Each record may comprisea plurality of attributes or data fields comprising data such as,product codes, product details (quantity, one or more productspecification parameters, vendor details, shipping details, user giftmessages), purchase details (financial account identifiers and otherdetails), user details (shipping addresses, loyalty program information,and the like), shipping details (timeline, routing details, transportdetails and the like), inventory details (warehouse information, and thelike), or the like. Although, at each processing stage, the associatedtechnology application/platform may operate on only a portion of theattributes, the rest of the attributes would also be required to beprocessed for subsequent operations by other downstream applications andfor transmission to an end user system after the completion ofprocessing. As discussed previously, the processed record data istransient and is transmitted from one application/platform to anothervia transient memory locations. Because the data is continuallytransformed and is only temporarily available, in the event of failureof the processing of a record, it is very difficult to determine thespecific transformation performed at each processing stage, much lessidentify a potential cause and undertake remedial actions.

Furthermore, these concerns are exacerbated in applications involvingfinancial transactions, where each electronic file may comprisehundreds, thousands or tens of thousands of records, each recordrepresenting an electronic financial transaction, where real-timedetermination of the status of the transaction processing, content ofthe modified transaction records at the transient memory location, anddetermination of the source of any data modifications in the dataprocessing, and subsequent correction for the completion of thefinancial transaction, is desired. Determining the particular stage ofprocessing (for example, determining a current technology applicationprocessing the record), and determining the content of the recordsthrough the multiple data processing events of numerous applications, inreal-time, is not practical in existing systems. As discussedpreviously, particularly in the case of current financial dataprocessing environments, the complexity of the data staging and movementactivities, and the transient nature of the modified data hinderstracking and determining status and content of electronic files beingprocessed at real time or near real-time for each and every activity,and/or mapping the modified data through the different transactionstages for the payment transactions the entity performs. Furthermore,data modifications in financial transaction record processing may hinderthe processing all together. The present invention alleviates the aboveconcerns and is directed to providing a novel technical solution thatrelates to monitoring, identifying and correlating changes to transientdata as a plurality of technology records are processed by a pluralityof applications, without increasing the processing time of the record(typically about one second) and without modifying platformapplications, as will be described in detail in this disclosure.

Embodiments of the present invention will now be described more fullyhereinafter with reference to the accompanying drawings, in which some,but not all, embodiments of the invention are shown. Indeed, theinvention may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein; rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. Like numbers refer to elements throughout. Wherepossible, any terms expressed in the singular form herein are meant toalso include the plural form and vice versa, unless explicitly statedotherwise. Also, as used herein, the term “a” and/or “an” shall mean“one or more,” even though the phrase “one or more” is also used herein.

In some embodiments, an “entity” or “enterprise” as used herein may beany institution employing information technology resources andparticularly technology infrastructure configured for large scaleprocessing of electronic files, electronic technology event data andrecords, and performing/processing associated technology activities. Insome instances, the entity's technology systems comprise multipletechnology applications across multiple distributed technology platformsfor large scale processing of technology activity files and electronicrecords. As such, the entity may be any institution, group, association,financial institution, establishment, company, union, authority or thelike, employing information technology resources.

As described herein, a “user” is an individual associated with anentity. In some embodiments, a “user” may be an employee (e.g., anassociate, a project manager, an IT specialist, a manager, anadministrator, an internal operations analyst, or the like) of theentity or enterprises affiliated with the entity, capable of operatingthe systems described herein. In some embodiments, a “user” may be anyindividual, entity or system who has a relationship with the entity,such as a customer. In other embodiments, a user may be a systemperforming one or more tasks described herein.

In the instances where the entity is a financial institution, a user maybe an individual or entity with one or more relationships affiliationsor accounts with the entity (for example, a financial institution). Insome embodiments, the user may be an entity or financial institutionemployee (e.g., an underwriter, a project manager, an IT specialist, amanager, an administrator, an internal operations analyst, bank telleror the like) capable of operating the system described herein. In someembodiments, a user may be any individual or entity who has arelationship with a customer of the entity or financial institution. Forpurposes of this invention, the term “user” and “customer” may be usedinterchangeably. A “technology resource” or “account” may be therelationship that the user has with the entity. Examples of technologyresources include a deposit account, such as a transactional account(e.g. a banking account), a savings account, an investment account, amoney market account, a time deposit, a demand deposit, a pre-paidaccount, a credit account, a non-monetary user profile that includesonly personal information associated with the user, or the like. Thetechnology resource is typically associated with and/or maintained by anentity.

As used herein, a “user interface” may be a graphical user interface.Typically, a graphical user interface (GUI) is a type of interface thatallows users to interact with electronic devices such as graphical iconsand visual indicators such as secondary notation, as opposed to usingonly text via the command line. That said, the graphical user interfacesare typically configured for audio, visual and/or textual communication.In some embodiments, the graphical user interface may include bothgraphical elements and text elements. The graphical user interface isconfigured to be presented on one or more display devices associatedwith user devices, entity systems, processing systems and the like.

As discussed previously, each “electronic data file” or “technologyevent data file” or a “data file” often comprises multiple technologyevent records (for example, hundreds, thousands or tens of thousands oftechnology event records). Each technology event record may comprisemultiple data elements or attributes containing electronic dataregarding one or more aspects of an electronic/technology activity. Insome instances, each technology event record may comprise technologyelements associated with type of activity, instructions for processingthe event record, technology resources involved, information associatedwith the users/entities/systems involved, technology platformapplications involved, processing events associated with each technologyapplication, activity attributes, time, location, person/system thatinitiated/performed the activity, and/or other aspects. Furthermore, thetechnology elements may by discrete components of the record, or thetechnology elements may merely refer to one or more portions of a singledata component in a record. Although referred to as “a technology eventrecord”, it is understood that, in some embodiments each activity may beassociated with multiple technology event records.

For example, in the instances where the electronic data files comprisefinancial information, each electronic data file may comprise multipletechnology event records, with each technology event record beingassociated with an electronic activity comprising a financialactivity/transaction. Furthermore, each record may comprise one or moretechnology elements associated with type of activity (for example,debit, credit, resource transfer), instructions for processing therecord (for example, type of processing), technology resources involved(for example, initiating resource/financial institution, receivingresource or financial institution, intermediate resource systems,domestic systems, international systems), technology platformsapplications involved (for example, technology data processingapplications, regulatory applications, internal applications),information associated with the users/entities/systems involved (forexample, initiating or first user name, first user account identifiers,receiving or second user name, second user account identifiers),activity attributes (for example, resource quantity/amount, inbound andoutbound currency), timestamp, and/or other aspects.

An electronic activity, also referred to as a technology activity, suchas a “resource transfer” or “transaction,” may refer to any activitiesor communication between a user or entity and the financial institution,activities or communication between multiple entities, communicationbetween technology applications and the like. A resource transfer mayrefer to a payment, processing of funds, purchase of goods or services,a return of goods or services, a payment transaction, a credittransaction, or other interactions involving a user's account. In thecontext of a financial institution, a resource transfer may refer to oneor more of: a sale of goods and/or services, initiating an automatedteller machine (ATM) or online banking session, an account balanceinquiry, a rewards transfer, an account money transfer or withdrawal,opening a bank application on a user's computer or mobile device, a useraccessing their e-wallet, or any other interaction involving the userand/or the user's device that is detectable by the financialinstitution. A resource transfer may include one or more of thefollowing: renting, selling, and/or leasing goods and/or services (e.g.,groceries, stamps, tickets, DVDs, vending machine items, and the like);making payments to creditors (e.g., paying monthly bills; payingfederal, state, and/or local taxes; and the like); sending remittancessuch as paychecks; loading money onto stored value cards (SVCs) and/orprepaid cards; donating to charities; and/or the like.

As discussed previously, embodiments of the present invention alleviatethe deficiencies of existing systems and achieve other advantages byproviding apparatuses (e.g., a system, computer program product and/orother devices) and methods for real time event capture, andtransformation of transient data for an information network.Furthermore, the present invention enables real-time tracking ofprocessing activities performed on individual records and the datacontained therein, by capturing and mapping event data using proctormodules, without requiring replacement or modification of existing dataprocessing applications and without slowing down the processing of therecord. Specifically, the present invention is embodied in technologyapparatuses (e.g., a system, computer program product and/or otherdevices) and methods for establishing existing technology applicationsand/or other technology applications and/or platforms in a technologyprocessing system environment for real time event capture, analysis,transformation and charting of transient data in an information network.Accordingly, the novel technology event processing system provides atechnical improvement over existing data processing systems, because thepresent invention allows for dynamic capture, comparison, mapping andanalysis of transient event data, in real-time, without any increases inprocessing time and speeds of record processing.

FIG. 1 illustrates a technology event processing system environment 100,in accordance with one embodiment of the present invention. Asillustrated in FIG. 1, a technology event processing system 108 isoperatively coupled, via a network 101 to a user device 104, to anentity server 106, and to a technology server 105. In this way, thetechnology event processing system 108 can send information to andreceive information from the user device 104, the entity server 106 andthe technology server 105. FIG. 1 illustrates only one example of anembodiment of the system environment 100, and it will be appreciatedthat in other embodiments one or more of the systems, devices, orservers may be combined into a single system, device, or server, or bemade up of multiple systems, devices, or servers. In this way, thetechnology platform module 200 of the technology event processing system108, a network of comprising technology platform applications, isconfigured to process, index, chart and evaluate one or more electronicfiles and the associated technology event records, and perform theassociated technology activities.

The network 101 may be a system specific distributive network receivingand distributing specific network feeds and identifying specific networkassociated triggers. The network 101 may also be a global area network(GAN), such as the Internet, a wide area network (WAN), a local areanetwork (LAN), or any other type of network or combination of networks.The network 101 may provide for wireline, wireless, or a combinationwireline and wireless communication between devices on the network 101.

In some embodiments, the user 102 may be one or more individuals orentities that may either provide the electronic files for processing,desire access to at least a portion of the technology event dataassociated with the electronic files or records that have either beenprocessed or are being processed, and/or the request access to dataassociated with the technology activities associated with the eventrecords. As such, in some embodiments, the user 102 may be associatedwith the entity and/or a financial institution that may desire one ormore data points associated with the processing of electronic filesassociated with the technology event processing system for payment orglobal payment processing.

FIG. 1 also illustrates a user system 104. The user device 104 may be,for example, a desktop personal computer, a mobile system, such as acellular phone, smart phone, personal data assistant (PDA), laptop, orthe like. The user device 104 generally comprises a communication device112, a processing device 114, and a memory device 116. The user device104 is typically a computing system that is configured to enable userand device authentication for access to technology event data. Theprocessing device 114 is operatively coupled to the communication device112 and the memory device 116. The processing device 114 uses thecommunication device 112 to communicate with the network 101 and otherdevices on the network 101, such as, but not limited to, the entityserver 106, the technology event processing system 108 and thetechnology server 105. As such, the communication device 112 generallycomprises a modem, server, or other device for communicating with otherdevices on the network 101.

The user device 104 comprises computer-readable instructions 110 anddata storage 118 stored in the memory device 116, which in oneembodiment includes the computer-readable instructions 110 of a userapplication 122. In some embodiments, the technology event processingsystem 108 and/or the entity system 106 are configured to cause theprocessing device 114 to execute the computer readable instructions 110,thereby causing the user device 104 to perform one or more functionsdescribed herein, for example, via the user application 122 and theassociated user interface.

As further illustrated in FIG. 1, the technology event processing system108 generally comprises a communication device 146, a processing device148, and a memory device 150. As used herein, the term “processingdevice” generally includes circuitry used for implementing thecommunication and/or logic functions of the particular system. Forexample, a processing device may include a digital signal processordevice, a microprocessor device, and various analog-to-digitalconverters, digital-to-analog converters, and other support circuitsand/or combinations of the foregoing. Control and signal processingfunctions of the system are allocated between these processing devicesaccording to their respective capabilities. The processing device, suchas the processing device 148, typically includes functionality tooperate one or more software programs and technology platformapplications based on computer-readable instructions thereof, which maybe stored in a memory device, for example, executing computer readableinstructions 154 or computer-readable program code 154 stored in memorydevice 150 to perform one or more functions associated with a technologyplatform module 200

The processing device 148 is operatively coupled to the communicationdevice 146 and the memory device 150. The processing device 148 uses thecommunication device 146 to communicate with the network 101 and otherdevices on the network 101, such as, but not limited to the entityserver 106, the technology server 105 and the user system 104. As such,the communication device 146 generally comprises a modem, server, orother device for communicating with other devices on the network 101.

As further illustrated in FIG. 1, the technology event processing system108 comprises the computer-readable instructions 154 stored in thememory device 150, which in one embodiment includes thecomputer-readable instructions 154 of the technology platform module200. In some embodiments, the computer readable instructions 154comprise executable instructions associated with technology platformapplications, proctor modules, memory locations, technology eventprocessing module and/or its components, associated with the technologyplatform module 200, wherein these instructions, when executed, aretypically configured to cause the applications or modules toperform/execute one or more steps described herein. In some embodiments,the memory device 150 includes data storage 152 for storing data relatedto the system environment, but not limited to data created and/or usedby the technology platform module 200. The technology platform module200 is further configured to perform or cause other systems and devicesto perform the various steps in processing electronic records, as willbe described in detail later on.

As such, the processing device 148 is configured to perform some or allof the data processing and event capture, transformation and analysissteps described throughout this disclosure, for example, by executingthe computer readable instructions 154. In this regard, the processingdevice 148 may perform one or more steps singularly and/or transmitcontrol instructions that are configured to cause technology platformapplications, proctor modules, event processing modules, entity server106, user device 104, and technology server 105 and/or other systems andapplications, to perform one or more steps described throughout thisdisclosure. Although various data processing steps may be described asbeing performed by technology platform applications, proctor modules,memory locations, technology event processing module and/or itscomponents and the like in some instances herein, it is understood thatthe processing device 148 is configured to establish operativecommunication channels with and/or between these modules andapplications, and transmit control instructions to them, via theestablished channels, to cause these module and applications to performthese steps.

Embodiments of the technology event processing system 108 may includemultiple systems, servers, computers or the like maintained by one ormany entities. FIG. 1 merely illustrates one of those systems 108 that,typically, interacts with many other similar systems to form theinformation network. In one embodiment of the invention, the technologyevent processing system 108 is operated by the entity associated withthe entity server 106, while in another embodiment it is operated by asecond entity that is a different or separate entity from the entityserver 106. In some embodiments, the entity server 106 may be part ofthe technology event processing system 108. Similarly, in someembodiments, the technology event processing system 108 is part of theentity server 106. In other embodiments, the entity server 106 isdistinct from the technology event processing system 108.

In one embodiment of the technology event processing system 108, thememory device 150 stores, but is not limited to, the technology platformmodule 200 comprising the technology platform applications and thetechnology event processing module, as will be described later on withrespect to FIG. 2. In one embodiment of the invention, the technologyplatform module 200 may associate with technology platform applicationshaving computer-executable program code that instructs the processingdevice 148 to operate the network communication device 146 to performcertain communication functions involving the technology server 105, theuser device 104 and/or the entity server 106, as described herein. Inone embodiment, the computer-executable program code of an applicationassociated with the technology platform module 200 may also instruct theprocessing device 148 to perform certain logic, data processing, anddata storing functions of the application.

The processing device 148 is configured to use the communication device146 to receive data, such as electronic data files comprising technologyevent records, receive requests for processing status and processedevent data, transmit processed event data and the like. In someinstances, the processing device 148 stores the data that it receives inits native format in the memory device 150, for example, in an off-diskdatabase associated with the data storage 152, described in detail withrespect to FIG. 2.

In the embodiment illustrated in FIG. 1 and described throughout much ofthis specification, the technology platform module 200 may perform oneor more of the functions described herein, by the processing device 148executing computer readable instructions 154 and/or executing computerreadable instructions associated with one or more technology platformapplications.

As illustrated in FIG. 1, the entity server 106 is connected to thetechnology event processing system 108 and may be associated with afinancial institution network. In this way, while only one entity server106 is illustrated in FIG. 1, it is understood that multiple networksystems may make up the system environment 100 and be connected to thenetwork 101. The entity server 106 generally comprises a communicationdevice 136, a processing device 138, and a memory device 140. The entityserver 106 comprises computer-readable instructions 142 stored in thememory device 140, which in one embodiment includes thecomputer-readable instructions 142 of an institution application 144.The entity server 106 may communicate with the technology eventprocessing system 108. The technology event processing system 108 maycommunicate with the entity server 106 via a secure connection generatedfor secure encrypted communications between the two systems forcommunicating data for processing across various applications.

As further illustrated in FIG. 1, in some embodiments, the technologyevent processing system environment 100 further comprises a technologyserver 105, in operative communication with the technology eventprocessing system 108, the entity server 106, and/or the user device104. Typically, the technology server 105 comprises a communicationdevice, a processing device and memory device with computer readableinstructions. In some instances, the technology server 105 comprises oneor more data processing applications configured for downstreamprocessing event records associated with the electronic files receivedfrom the technology event processing system. These applications may beoperated by the processor executing the computer readable instructionsassociated with the technology server 105, as described previously. Insome instances, the technology server 105 is owned, operated orotherwise associated with third party entities, while in otherinstances, the technology server 105 is operated by the entityassociated with the systems 108 and/or 106. Although a single externaltechnology server 105 is illustrated, it should be understood that, thetechnology server 105 may represent multiple technology serversoperating in sequentially or in tandem to perform one or more dataprocessing operations.

It is understood that the servers, systems, and devices described hereinillustrate one embodiment of the invention. It is further understoodthat one or more of the servers, systems, and devices can be combined inother embodiments and still function in the same or similar way as theembodiments described herein.

FIG. 2 illustrates the technology platform module environment 200 forreal time event capture, transformation and analysis of transient dataassociated with the information network 101. In some embodiments,computer readable instructions 154, when executed by the processingdevice 148 of the technology event processing system 108 (hereinafterreferred to as “the system”), are typically configured to cause themodules, applications, and other components of the technology platformmodule environment 200 to perform one or more functions as describedherein. The technology platform module 200 typically comprises a dataprocessing module 201 comprising a plurality of processing applicationsand associated transient memory locations as described below. The dataprocessing module 201 of an entity, and specifically the technologyplatform applications are configured to process records associated withelectronic data files, such as electronic product orders, financialresource transfers or payment transfers and the like. As discussedpreviously, each electronic data file or technology event data filetypically comprises multiple technology event records (for example,hundreds, thousands or tens of thousands of technology event records).Each technology event record typically further comprises multiple dataelements or attributes containing attribute data regarding anelectronic/technology activity (such as a resource transfer activity).Typically, once the electronic file (such as an electronic file relatedto resource transfer activities) is received for processing, theelectronic file is fragmented and associated technology event recordsare processed individually, separate from the electronic file. The eventdata in each of the technology event records is typically transformed bya plurality of technology platform applications, in order to perform thetechnology activity associated with the record.

In this regard, the technology platform module 200 typically comprisesmultiple technology platform applications, such as a technology platformapplication 1 (205), a technology platform application 2 (215), toexecute the specific data processing operations. The technology platformmodule 200 may further comprise technology platform applications 3, 4, .. . and so on (not illustrated), wherein each technology platformapplication is configured to perform at least one processing operation(also referred to as a processing event) on the technology eventrecords. As illustrated, the technology platform applications aretypically configured to process the technology event records in asequential manner, although in some embodiments two or more technologyplatform applications may process the records in tandem. The technologyplatform applications are typically configured to process the eventrecords in a series of processing events, each processing eventtypically resulting in processed data or processing event data.Processing of the technology event records comprises modifying the eventdata by transforming the associated event data, formatting the eventdata and the like, for the completion of the processing event at thetechnology application and/or for ensuring compatibility with thesucceeding technology application. In this regard, the format,programming language, character set, syntax and the like of record datain one or more attributes of the event records are modified as the datais processed by a technology platform application to execute theassociated processing event. As discussed previously, format,programming language, character set and/or syntax, of the event recordsare successively modified/transformed by the technology platformapplications. These modifications may comprise modifications performedby the technology platform applications while the records are processedby the applications, inadvertent data alterations caused by thetechnology applications, middleware or other components, and/or dataalterations performed by one or more users using the technologyapplications or other components. In some instances, the datamodifications performed by the technology applications and dataalterations by users/personnel are necessary and required for processingand/or are often unavoidable, while the data alterations comprisingprocessing errors by applications, or inadvertent alterations bypersonnel are often undesirable. Although, in some instances, alterationof the data content of records by either the systemcomponents/applications or the users, i.e., the record data contained inthe one or more attributes may be undesirable and hence eschewed.

As further illustrated by FIG. 2, each technology platform applicationis associated with a transient memory location. Although two transientmemory locations (210, 220) are illustrated, it is understood that thetechnology platform module 200 may further comprise other transientmemory locations associated with any additional technology platformapplications (3,4, . . . ) that the module may comprise. As such, eachtechnology platform application is configured to store processed eventrecords in a transient data queue, or another suitable data structure,in the transient memory location for retrieval by the subsequentprocessing by another technology platform application. The transientdata queue is implemented using a suitable data structure such as alinked list or a doubly linked list. The transient data queue isassociated with a queue type, chosen based on the associated technologyplatform application. The queue types comprise a linear queue, apriority queue, a circular queue, a double-ended queue and the like.Furthermore, the transient data queue is configured for enqueuing orenqueue operations, i.e. addition of event records to the queue at arear terminal position of the queue as the processed records arereceived from the preceding technology application, and dequeuing ordequeue operations, i.e. removal of event records from a front terminalposition of the queue when the records are retrieved by a succeedingtechnology application for further processing. The configuration of rearterminal position and the front terminal position typically varies basedon the queue type. Although termed as a data queue, it is understoodthat other data structures such as stacks may also be employed.

As such the transient memory locations are configured to store processedevent data associated with the records being processed, temporarilyuntil the records are retrieved by succeeding technology platformapplications using a dequeue operation. The dequeue operation maycomprise deletion of data from the data queue, overwriting of the eventdata with other event records, and the like, once the record isretrieved by the succeeding technology application. As such, in someembodiments, the transient memory location is implemented in a fixedmemory location in physical memory hardware, such as the physicalstorage medium of memory device 150. In other embodiments, the transientmemory location is implemented by using a virtual data buffer insoftware, pointing at a location in the physical memory, such as thephysical storage medium of memory device 150. In some embodiments, thedata queues at transient memory locations are operated using RAM totemporarily store the event record data for quicker access andretrieval, although hard disk drives may also be employed. In someinstances, after completion of the processing by the technology platformapplications, the processed records are transmitted to the technologyserver 105, for any further operations. As discussed previously, becausethe transformed event data associated with the processing events at thetechnology platform applications is only temporarily available at thetransient memory locations, it is extremely difficult and often notpossible to track the processing of the records, much less analyze,compare and chart the processed event data at the various processingevents of the technology platform applications, using solely thetechnology platform applications and the transient memory locations. Thepresent invention provides a novel solution by implementing proctormodules and a technology event processing module that alleviate theaforementioned concerns without increasing the processing time orprocessing speed of the records. Furthermore, the proctor modules andthe technology event processing module may be integrated with existingtechnology platform applications in an information network, withoutrequiring modifications to the existing application structures.

As illustrated by FIG. 2, the technology platform module 200 furthercomprises a data capture and analysis module 202 for real-time capture,analysis and mapping of transient event data of the data processingmodule 201. As such, the data capture and analysis module 202 describedherein is configured to capture, analyze and chart processing of eventrecords of any particular data processing module 201 of an entity. Thedata capture and analysis module 202 can be easily configured andoperatively coupled to an existing data processing module 201, withminimal or no modifications to the data processing module 201 and/or thedata capture and analysis module 202. The data capture and analysismodule 202 typically comprises one or more proctor modules associatedwith the transient memory locations. The proctor modules are configuredfor real time capture of event data as the event records undergoprocessing events at various technology platform applications.Typically, the technology platform module 200 comprises at least twoproctor modules. The proctor modules are typically employed at transientmemory locations, whose processed record data is required to be analyzedor charted. For instance, FIG. 2 illustrates a proctor module 230associated with transient memory location 210 and a proctor module 240associated with the transient memory location 220. However, thetechnology platform module may comprise additional proctor modulesassociated with other transient memory locations (3, 4, . . . ).Furthermore, each proctor module is typically associated with adownstream proctor queue memory location. For instance, FIG. 2illustrates a proctor queue memory location 1 (235) associated with theproctor module 230 and proctor queue memory location 2 (245) associatedwith the proctor module 240.

As such, the proctor module (230, 240, . . . ) is configured to capturethe event data in the transient data queues of the associated transientmemory location (210, 220, . . . ), in real-time, and store thereplicated data in an associated proctor queue memory location (235,245, . . . ). Capturing the transient data queue comprises replicatingeach of the processed event records as they are added to the transientdata queue, in real time or near real time after the enqueue operations,and before the dequeue operations. Typically, the proctor module (230,240, . . . ) is configured such that addition of data to the associatedtransient memory location automatically triggers the proctor module fordata replication, in real time, without requiring transmission ofadditional instructions. In some embodiments, the proctor modulecomprises a daemon program such as a unix daemon program, configured forreplicating the event data in the transient data queues and storing thereplicated data in the associated proctor queue memory location.Furthermore, in some embodiments, the proctor queue memory locations aretransient memory locations, similar to those described previously, thatare configured to store the replicated data (for example, in transientdata queues) until it is transmitted to, or retrieved by the technologyevent processing module 250.

The technology platform module 200, and the data capture and analysismodule 202 in particular, further comprises a technology eventprocessing module 250 in operative communication with the proctormodules and the proctor queue memory locations. The technology eventprocessing module 250 is configured for transformation, analysis andreporting of the captured or replicated event data in real time or nearreal time. Specifically, the technology event processing module 250comprises a technology data logging application 255, an eventstandardization module 260, a charting module 265, a dynamic event dataevaluation application 270 and an indexing module 280, in operativecommunication with each other. The technology event processing module250 is in operative communication with an off-disk database 290comprising a native format event database 292 and an event data payload294. In some embodiments, the off-disk database 290 is associated withthe data storage 152 of the technology event processing system 108, toensure the security and safety of the processed event data. In otherembodiments, at least a portion of the off-disk database 290 may beassociated with external systems or external databases, such as theentity server 106, the technology server 105, and the like. In someembodiments, the off-disk database employs data storage virtualizationfor the processed event data, such as block virtualization, filevirtualization and the like. In some embodiments, the off-disk database290 is a virtual tape. In some embodiments, the off-disk database 290 isa virtual tape library (VTL) with a physical storage component such ashard disk storage, although tape drives may also be employed. Here, insome instances, the VTL comprises Serial Attached SCSI (SAS) or SerialAT Attachment (SATA) disk arrays as the storage component. These arrayenclosures enhance the scalability of the off-disk database 290, becausethe storage capacity may be increased by merely adding additional diskdrives and enclosures.

The technology data logging application 255 is configured to receive thecaptured processed event data from the proctor queue memory locations(235, 245, . . . ) and assign unique processing event identifiers toeach captured event and log the indexed event data to an event indexmemory location 282 of the indexing module 280. In some embodiments, thetechnology data logging application 255 is configured to store indexedcaptured event data records in the native format event database 292,such that the associated attribute data is stored in the native formatthat it was captured in. Typically, the event data is stored as eventrecords such that each captured event is associated with an eventrecord, wherein each event data record is stored at a specific memorylocation address in the database 292. Furthermore, in some embodiments,the assigned unique processing event identifier is stored in apredetermined identifier field of the event record in the database 292,while the captured attribute data is typically stored in one or morefields of the event record in its native format. In some instances, thenative format event database 292 comprises two dimensional arrays,multidimensional arrays, relational databases and the like, that areconfigured to store the indexed captured event data records. In someinstances, the native format event database 292 comprises a structuresimilar to that described with respect to the off-disk database 290.

The technology data logging application 255 is further configured tostore an index of the event data stored in the native format eventdatabase 292. In this regard, for each captured processing event record,the assigned unique processing event identifier and the memory locationaddress of the event data stored in native format at database 292, arecorrelated and stored in the event index memory location 282. As such,in some instances, the event index memory location 282 comprises one ormore logs or indices, each index comprising a unique processing eventidentifier and a memory location address indicating the storage locationof the data. As such, the event index memory location 282 comprises twodimensional arrays, multidimensional arrays, relational databases or thelike.

The event standardization module 260 is configured to transform thecaptured event data into a predetermined format for further analysis. Assuch, the format of the technology event data records in the receivedelectronic files may vary from one file to another, within the recordsof the same file, and/or within data attributes of a single record. Asdiscussed previously, format, programming language, syntax and/orattributes, of the event records are successively modified by thetechnology platform applications, associated components or associatedusers. Therefore, at least a portion of the captured processed eventdata of certain event record from a first proctor module associated withmodifications performed by a first technology platform application, isoften distinct and unalike the captured processed event data of the samerecord from a third proctor module associated with modification by athird technology application, downstream of the first application. Theevent standardization module 260 is configured to transform the capturedevent data received from the technology data logging application 255 toa predetermined standard format, standard programming language andstandard syntax and structure. This standardization enables mapping ofevent records described in detail elsewhere in this disclosure.

The charting module 265 is configured to map the captured processingevent records with upstream and downstream processing event records forthe each origination event record received at the technology platformapplication 205. In this way, the charting module 265 is configure toconstruct mapped event metadata, reflecting the course of the variousprocessing events performed by the technology platform application andthe associated modifications in the record data. Furthermore, thecharting module 265 is configured to write, for each event record, thetransformed/standardized mapped event data comprising various processingevent data records associated with various stages of processing on themapped event data payload 294, in a manner similar to that describedwith respect to the database 292. Specifically, the charting module 265is configured to store each of the transformed/standardized event datarecords at specific memory location addresses. The mapped event datapayload 294 typically stored the standardized paired event data in apredetermined file format. For instance, this predetermined file formatmay be a file under folder (FUF) format. In some embodiments, the mappedevent data payload 294 comprises a distributed storage framework, suchas a Distributed File System (DFS). In addition, the charting module 265is configured to log the mapped event metadata to an index in thematching index memory location 284 of the indexing module. In thisregard, the matching index memory location 284 may correlate the memorylocation addresses of processing event data records stored in the mappedevent data payload 294, that are related to the processing of a singleorigination technology event record. These features are described indetail with respect to FIG. 4 elsewhere in this disclosure. The dynamicevent data evaluation application 270 is configured to dynamicallycompare multi-attribute mapped originated technology data and processedevent data, as will be described in detail later on.

As discussed previously, in some embodiments, computer readableinstructions 154, when executed by the processing device 148, aretypically configured to cause the technology platform applications,proctor modules, technology data logging application 255, eventstandardization module 260, charting module 265, indexing module 280,dynamic event data evaluation application 270, and other components ofthe technology platform module environment 200 to perform one or morefunctions as described herein.

FIG. 3 illustrates a process map 300 for processing of electronic datafiles, in accordance with some embodiments of the invention. Asdiscussed previously, multiple technology platform applicationstypically process technology event records in received electronic file,by performing a series of discrete processing events. As illustrated atstep 305, a first or origination technology platform application, suchas application 205, receives one or more technology event data files orelectronic data files for processing. This data file is typicallyreceived at the technology event processing system 108, from the userdevice 104, entity server 106 and the like. For example, the system 108may receive one or more electronic files (for example, files associatedwith electronic product orders, payment processing and the like) forprocessing, each file comprising one or more technology event records(for example, technology event records associated with a resourcetransfer activity of executing a shipment order, a payment transfer, andthe like), from a user 102, via a user interface of the user application122 of the user device 104. The received electronic files are referredto as origination electronic files and the event records containedtherein are referred to as origination event records. On receiving theelectronic file for processing, the first or origination technologyapplication typically analyzes the origination file, identifies andextracts the one or more origination event records contained within asdiscrete event records for processing. In this regard, in someembodiments, the received electronic file is fragmented into a pluralityof discrete event records for data processing. The originationtechnology platform application then creates a first or originationtransient data queue at a first transient memory location at step 310.Subsequently, the origination technology platform application places theextracted origination event records and the associated event data in theorigination transient data queue.

In this regard, in some instances, the origination platform applicationperforms a series of enqueue operations to place each origination eventrecord, individually, on the origination data queue at step 310, such asthe transient memory location 210. In some embodiments, placing theorigination event records, individually, on the origination queuecomprises modifying the event records. In this regard, the system 108,via the origination technology application, may augment each of theorigination records with a timestamp, the name or identifier associatedwith the origination data file that the record was extracted from, theuser or system that transmitted the origination file, and the like.Furthermore, in some embodiments, the origination technology platformapplication may analyze the origination event records and place them inthe origination queue in a suitable order or succession based on apredetermined criteria such as timestamp, activity deadline, priority,format of the origination record, memory size, estimated completiontime, estimated number of processing events to complete the technologyactivity and the like. In some instances, placing the transient eventdata on the queue is configured to cause the origination event recordsto be processed individually and the associated technology activities tobe performed individually, separate from the origination electronic fileand from one another. For example, a plurality of origination recordsplaced in the origination transient data queue in a suitable order maycomprise origination records extracted from two or more originationelectronic files. In some instances, the origination transient dataqueue is a multi-level queue where the origination activity records aregrouped into two or more sub-queues based on a suitable criteria such asformat of the origination record, priority, data content of thepredetermined attribute, and the like. In this regard, each sub-queuemay be assigned a sub-queue processing priority. Furthermore, additionof event records to the origination transient data queue triggers,automatically, the associated proctor module for data replication, inreal time, without requiring transmission of additional instructions.

In addition, placing the origination event records on the originationtransient data queue is configured to trigger, automatically and in realtime, a second technology platform application. The second technologyplatform application then extracts the origination event records fromthe origination transient data queue at step 315. This extraction istypically performed by a series of dequeue operations, using a suitablescheduling algorithm such as first in first out (FIFO), earliestdeadline first (EDF), shortest job first (SJF), priority scheduling andthe like. In the instances where the origination data queue is amulti-level queue, the second technology platform application maydequeue the origination records from sub-queues with higher processingpriorities first and then by employing a suitable scheduling algorithmwithin the sub-queues, thereby ensuring optimal utilization ofprocessing resources and reducing processing time, while ensuring thathigh priority records are processed first.

Next, the second technology platform application formats or transformsthe retrieved origination event records. The second technology platformapplication further analyzes, for each event record, the event data todetermine the next technology platform application, for example thirdtechnology platform application, that the record has to be routed to forthe next processing event. In this regard, in some instances, the secondtechnology platform application may perform the formatting operationsand route a retrieved technology event record to the determinedtechnology platform application, before dequeuing the next originationrecord from the origination data queue. Furthermore, in someembodiments, formatting the event record comprises transforming thetechnical language, syntax, attribute formatting, character set (forexample, Binary Coded Decimal (BCD), ASCII, Unicode, Extended BinaryCoded Decimal Interchange Code (EBCDIC), and the like), characterencoding system of the data and the like into a predetermined standardformat and/or into a predetermined format required for processing by thesubsequent technology platform application. Furthermore, dequeuing anevent record from a transient data queue, such as the origination dataqueue, typically results in the record being removed, overwritten orotherwise deleted from the queue, to ensure that only the most currentprocessed version of the event record is available at a time. Therefore,the present invention provides a novel solution by implementing theproctor module to replicate the event record data before it is erasedfrom the transient memory location when the record is transmitted forsubsequent processing.

Routing the event record further comprises adding or enqueuing theprocessed event record to a second transient data queue associated withthe subsequent technology platform application for further processing ofthe event record, as illustrated by step 320. As an example, the secondtechnology platform application may route, sequentially, a first eventrecord to a transient data queue associated with a third technologyapplication, a second event record to a transient data queue associatedwith a fifth technology application, a third event record to a transientdata queue associated with a fourth technology application, and so onuntil all the event records in true first/origination transient dataqueue have been dequeued, formatted and routed for their subsequentprocessing. Adding or enqueuing the processed event data to the secondtransient data queue is typically substantially similar to the processpreviously described with respect to step 310.

As illustrated by step 325, the subsequent technology processingapplication, such as a third technology platform application, thenperforms a dequeuing operation to retrieve the processed event recordfrom the second transient data queue. This dequeuing operation istypically substantially similar to the retrieval operations describedwith respect to step 315. The third technology platform application thenperforms a first processing operation on the retrieved transient eventdata of the event record. This processing operation typically involvesmodification of the event record and the associated event data, forexample by transforming, augmenting, truncating, formatting, and/orappending the event data and/or the associated attributed. As such, thecontents, format, programming language, syntax, character encoding,character set and/or attributes, of the event records may modifiedduring the first processing operation or processing event performed bythe third technology platform application. In some instances, themodifications performed by the technology application may also compriseundesirable modifications due to processing errors or other inadvertentmodifications due to the functioning of the platform application and/orassociated middleware and other components. In some instances, themodifications may also comprise necessary data alterations performed byusers/personnel for continued downstream processing and/or inadvertentalterations or errors by users that may be undesirable for, or that mayhinder downstream processing of the records. After completion of thefirst processing operation or the processing event, the third technologyplatform application, typically determines the next application such asa fourth technology application that the processed event record has tobe routed to for subsequent processing. Subsequently, the thirdtechnology platform application may add the processed event record to athird transient data queue associated with the fourth technologyplatform application, as illustrated by step 330. The processingoperations then continue at steps 335, 340, 345, and so on, in a mannersimilar to the process described with respect to steps 315, 320, 325 and330. In some embodiments, after completion of the various processingoperations or processing events by the technology platform applications,the completely or partially processed event record may be transmitted toanother system, such as the technology server 105.

As discussed previously, addition or enqueuing of the event record to atransient data queue is configured to trigger, automatically, anassociated proctor application. As illustrated by step 360 of FIG. 3, afirst proctor application is triggered, automatically, to capture theorigination event record, comprising record data, attributes and thelike, added to the origination transient data queue at step 310.Typically, this capture or replication occurs, in real-time, after theenqueuing operation and before the record is dequeued for downstreamprocessing. Similarly, FIG. 3 also illustrates capture of processedevent records from a fourth transient data queue by a second proctorapplication, at step 380. For each event record, the first proctorapplication captures the origination event record in its native state asit is added to the origination transient data queue, and a secondproctor application captures the processed event record, in its nativestate, as it is added to the fourth transient data queue. Therefore,event data of the record as it was received in the origination file iscaptured, along with the modified event data after the requisiteprocessing/modification of the event record by the fourth processingplatform application at step 335 and processing at the precedingprocessing steps 312 and 325. Although, FIG. 3 illustrates proctorapplications associated with the first and fourth transient data queuesas an example, some or all of the other transient data queues (such assecond and third transient data queues illustrated at steps 320 and 330)may also be associated with proctor applications for capture ofprocessed event data at each step. In addition, in some embodiments, theproctor module comprises a single proctor application, which isconfigured to capture transient event records, in real time, as they areadded to various transient data queues.

Subsequently, the proctor applications generate an event payloadcomprising captured transient record data, as illustrated by steps 370and 390. Specifically, the first proctor application, such as proctormodule 230, is configured to construct a first proctor queue, such as atmemory location 235, comprising the captured origination records, atstep 370. As such, the first proctor application is configured tocapture the origination event record data in the origination transientdata queue, in real-time, and store the replicated data in theassociated first proctor queue, for example, by using an enqueueoperation. Similarly, the second proctor application is configured tocapture the processed event record data in the fourth transient dataqueue, in real-time, and store or add the replicated/captured data to anassociated second proctor queue, as illustrated by step 390. In theinstances where there are additional proctor applications, each of theadditional proctor applications are also typically configured to add thecaptured event records to associated proctor queues. In someembodiments, the proctor queues are similar to the transient data queuesin structure and operation. Typically, addition of the captured eventdata to a proctor queue is configured to trigger, automatically and inreal time, multi-attribute event data transformation, processingevaluation and data mapping by the technology event processing module250, as indicated by step 400. The multi-attribute event datatransformation, processing evaluation and data mapping process performedby the processing module 250, will be described in detail elsewhere inthis disclosure, with respect to the process map 400 illustrated by FIG.4.

As an illustrative example, the processing of the electronic files willnow be described in the context of processing electronic filescomprising resource transfer or financial activity data, such as apayment file for an organization. At step 305, the first or originationtechnology platform application, such as application 205, receives oneor more technology event data files or electronic data files, comprisingfinancial activity data, for processing. Here, each electronic data filemay comprise multiple technology event records (for example, hundreds,thousands or tens of thousands of records), with each technology eventrecord being associated with an electronic activity comprising afinancial activity/transaction such as a resource transfer, alsoreferred to as a payment transfer. Furthermore, each record may compriseone or more technology attributes associated with type of activity ortransaction (for example, debit, credit, resource transfer),instructions for processing the record (for example, type ofprocessing), technology resources involved (for example, initiatingresource/financial institution, receiving resource or financialinstitution, intermediate resource systems, domestic systems,international systems), technology platforms applications involved (forexample, technology data processing applications, regulatoryapplications, internal applications), information associated with theusers/entities/systems involved (for example, initiating or first username, first user account identifiers, receiving or second user name,second user account identifiers), activity attributes (for example,resource quantity/amount, inbound and outbound currency), timestamp,and/or other aspects. In some embodiments, the financial activityrecords in the electronic files relate to payment processing requests(also referred to as resource transfer activates), with each recordcomprising financial activity data required for completing the paymentprocessing activity. The payment processing activity may comprise apayment transfer or resource transfer from a first account associatedwith a first user/entity at a first location to another second account,typically associated with a second individual/entity at the same ordifferent location (for example, a different country).

On receiving the origination electronic file for processing, the firstor origination technology application typically analyzes the originationfile, identifies and extracts the one or more origination financialactivity records contained within and places the extracted originationevent financial activity records and the associated event data in theorigination transient data queue at step 310. Typically, the firsttechnology application is an activity origination application,configured for creation, submission and logging of an online orfile-based payment transfer request and associated attribute data. Next,the second technology platform application, such as middleware, extractsthe origination financial activity records from the originationtransient data queue at step 315. Subsequently, the second technologyplatform application formats the retrieved origination financialactivity records and determines the next technology platformapplication, for example the third technology platform application,associated with the next processing event. The second application maythen route the financial activity record to the second transient dataqueue associated with the subsequent technology platform application forfurther processing of the event record, as illustrated by step 320.

As discussed previously, the processing operations then continue atsteps 325, 330 335, 340, 345, and so on, to complete the financialactivity, for example resource transfer or payment transfer. The varioustechnology platform applications associated with the processingoperations/events at steps 325, 335, 345 and so on, may comprise apre-processing activity request routing and formatting application, anactivity request workflow initiation application, a post processingactivity request routing and formatting application, a data integrity orsanctions checking application, activity accounting application, and thelike. Two or more of these technology platform applications may beemployed, typically, in sequence to processes the activity recordsassociated with the electronic files. The pre-processing activityrequest routing and formatting application is typically configured formiddleware based movement and formatting of payment origination requestdata, such that each payment request is prepared and forwarded to thecorrect processing platform for workflow orchestration and successfulcompletion of the payment request. Furthermore, the activity requestworkflow initiation application is typically configured to forinitiation of programmed workflow. The programmed workflow is configuredto successfully auto-orchestrate the payment through the various stepsthat are required for the successful completion of a payment request orresource transfer request. The post processing activity request routingand formatting application is configured for middleware based movementand formatting of payment origination request data that ensures thateach payment request is correctly prepared and forwarded to the dataintegrity checking application. The system is configured to transmit theprocessed technology event record/data to an internal/external dataintegrity checking application, for example, after determining that thecontents of the processing record have not been altered/modified atblock 608 described later on with respect to FIG. 6. In some instances,the system is further configured to initiate the resource transfer orpayment transfer activity based on receiving an indication of asuccessful integrity check of the processed record.

Initiation of the resource transfer or payment transfer comprises, insome instances, transmitting the processed event records to one or moreinternal, one or more external (such as entity server 106) or thirdparty systems and applications (such as technology server 105) such asother financial institution applications, financial servicesapplications, clearing house applications, governmental applications,payment networks and other electronic funds transfer applications, forcompletion of the payment transfer or resource transfer activity. Inthis regard, these applications may perform one or more of dataintegrity checking, clearing, foreign exchange, debiting/crediting,settlement operations to complete the resource/payment transferactivity.

Other technology platform applications may comprise a payment settlementapplication, payment data transformation application, payment clearingapplication, and the like. Addition or enqueuing of the event record toa transient data queue by the platform applications is configured totrigger, automatically, an associated proctor application as describedpreviously.

FIG. 4 illustrates a process map 400 for multi-attribute event datatransformation, processing evaluation and data mapping process,typically performed by the technology event processing module 250. Asillustrated by step 405, the technology data logging application 255 isconfigured to retrieve processing event data from the proctor queues,often in real time as they are enqueued at the proctor queue memorylocations. Typically, the technology data logging application 255assigns a unique processing event identifier to each retrieved eventrecord. Next, as illustrated by step 410, for each event record, thetechnology data logging application typically logs the event metadata toan index of the event index memory location 282. Here, in someembodiments, the event record is augmented to store the assigned uniqueprocessing event identifier in a predetermined identifier field. Assuch, in some instances, the event index memory location 282 comprisesone or more logs or indices, each index comprising a unique processingevent identifier and accompanying event record metadata, for example indistinct fields.

As discussed previously, each event record comprises a plurality ofattributes or fields of event data associated with various facets of theevent records and associated technology activity. Since the event recordis often transmitted to the associated entity after processing andcompletion of the associated technology event, the origination eventrecord often comprises data attributes that may be required by theentity for post-completion analysis, record and report creation andpost-completion routing. For instance, an event record often comprises1000-2000 attributes or fields of event data. In some embodiments, thetechnology data logging application 255 is configured to store indexedcaptured event data record in its entirety in the native format eventdatabase 292, such that the associated attribute data is stored in thenative format that it was captured in, as indicated by step 415. Inaddition, in some instances, the technology data logging application 255logs the event record to an index comprising the assigned uniqueprocessing event identifier and accompanying event record metadatacomprising a predetermined portion of the event record attributes. Insome instances, the predetermined portion of event record attributes atereceived from the user. In some instances, metadata and/or thepredetermined portion of record attributes comprises record attributesthat are least likely to be modified in the course of processing of thetechnology event records. Here, in some instances, the technology datalogging application may determine the portion of the record attributesthat are typically required or necessary for execution of event dataprocessing steps and/or completion of the technology activity.Modification of data contained in such attributes may hinder theprocessing of the record itself at the technology platform applications,or even the completion of the associated technology activity, andtherefore such attributes are least likely to be modified. Therefore,the system may log this portion of data attributes, i.e., the datacontents of the portion of attributes as metadata. For instance, thetechnology data logging application may identify 10 record attributesfields out of 2000 total attributes of the record, and log them as theevent metadata.

Next, the event standardization module 260 is configured to transformthe captured event data into a predetermined format, as illustrated bystep 420. The event standardization module 260 is configured totransform the captured event data received from the technology datalogging application 255 to a predetermined standard format, standardprogramming language and standard syntax and structure. In someembodiments, the standardization module transforms only a portion of theevent data, such as the event metadata. Next, the event standardizationmodule is configured to establish index entries into event matchingtables and construct composite indices based on event attributes.Typically, these composite indices are constructed based on the eventrecord metadata and the index entries are stored as a record of amatching table in the matching index memory location 284.

The charting module 265 is configured to map the captured processingevent records with upstream and downstream processing event records forthe each origination event record received at the technology platformapplication 205. Specifically, for each standardized event record, thecharting module is configured to analyze the event data to determine theprocessing event type at step 425. In this regard, the system mayanalyze predetermined portions of the event record, for example eventmetadata to determine whether the even record is an origination eventrecord or a processing event record (also referred to as a processedevent record) that has been processed by one or more technology platformapplications. Based on determining that the event record is anorigination event record, the system then automatically, assigns aunique activity identifier to the origination record, at step 430. Theunique activity identifier assigned to origination event records may bedifferent from or similar to the unique event identifier assigned to therecords in retrieval from the proctor module. Based on determining thatthe event record is a processing or processed event record, the systemproceeds to analyze the processing event record. Consequently, at step435, the system/charting module matches each processing event record toan origination event record identified at step 430. The technicalprocess of matching the records is described in detail with respect toFIG. 5 elsewhere in this disclosure. As discussed previously, a singleorigination record may undergo a plurality of processing operations atthe technology platform applications resulting in a plurality ofprocessing records associated with the single origination record. Hence,each processing event record is mapped to only one origination eventrecord. Next, the system assigns the unique activity identifier of themapped origination event record to the processing event record at step440. In this regard, in some embodiments, assigning the unique activityidentifier of the mapped origination event record comprises augmentingthe processing event record to include the unique activity identifier ofthe mapped origination event record, for example by creating a newattribute or field with the data. Typically, the unique activityidentifier enables tracking of the processing of the origination eventrecord through processing by the plurality of technology applicationsand determining if the record data has been modified in the course ofthe processing.

In this way, the charting module 265 is configured to construct mappedevent records, reflecting the course of the various processing eventsperformed by the technology platform application and the associatedmodifications in the record data. Furthermore, the charting module 265is configured to write, for each mapped event record, thetransformed/standardized event data of the mapped/matched records on themapped event data payload 294 of the off-disk storage database 290, in amanner similar to that described with respect to the database 292. Here,the charting module 265 typically writes all of the plurality ofattributes of the event records to the off-disk storage. In addition,the charting module 265 is configured to log the mapped event metadatato an index in the matching index memory location 284 of the indexingmodule, as indicated at step 450. Consequently, the dynamic event dataevaluation application is configured to dynamically comparemulti-attribute mapped event records to determine if any modificationsto the event data were performed in the course of data processing, atstep 460, as will be described with respect to FIG. 6.

FIG. 5, illustrates a high level process flow 500 for mapping ofprocessing event record with the origination event records, at thecharting module 265. Conventional processing methods typically matchfiles or documents by reading and matching the data contained within.For example, by comparing the text or contents of two files, typicallycharacter by character. However, such comparisons of bulky files whilebeing intensely time consuming, also devour large amount of processingand memory resources. Typically, each technology event record undergoesabout 40 processing operations and is processed within about 1-2seconds. However, implementing string comparison each attribute data ofrecord data of a particular origination event record containingthousands of attributes, with corresponding attribute data of 40versions each of processed event records of tens of thousands ofcaptured records, infinitely compounds time and processing drawbacks ofconventional comparison methods, if not rendering such a processinfeasible.

Another crucial drawback of conventional comparison methods is that,they simply fail to match event records whose data has been modified inthe course of processing. As discussed previously, processing operationsby the technology platform applications involve modification of theorigination event record and the associated event data. For examplecontents, format, programming language, syntax and/or attributes, of theorigination event records may successively modified during theprocessing operations/events performed by the technology applications,and such modifications may be desired to be identified and analyzed.Furthermore, the technology platform applications operate on differentmainframe, processing language configurations and distinct charactersets. For example, the received electronic data file may be associatedwith an XML (Extensible Markup Language) format and may comprise anorigination event record in the XML format. The extracted event recordadded to, and captured by the proctor module from the transient queuewould be present in the XML format. The subsequent technology platformapplication may be associated with an EBCDIC (Extended Binary CodedDecimal Interchange Code) format and may transform the origination eventrecord to the EBCDIC format for the processing operation. The processedevent record added to, and captured by the proctor module from thetransient queue would be present in the EBCDIC format. Because thecharacter sets, syntax and formats of XML are distinct from EBCDIC,conventional comparison methods fail to match the origination eventrecord with the processed event record even if the content of therecords remains unchanged, much less matching the records when thecontents of the event data is modified/altered.

The novel processing method and architecture described in the high levelprocess flow 500, alleviates the aforementioned concerns and provides anovel architecture that is configured to match origination event datarecords with their processed event counterparts with same or differentformats, even if the contents of the event data have been modified, inreal time or near real time, and without requiring large capacities ofprocessing and memory resources. Specifically, at block 502, thetechnology data logging application 255, determines the event metadata.The application 255, typically identifies the metadata for all of thecaptured event records as they are received from the proctor queues. Asdiscussed previously, the metadata typically comprises the predeterminedportion of the plurality of technology attributes, for exampleattributes that are least likely to be modified during the sequentialprocessing of the technology event records by the plurality oftechnology applications. For instance, the system may determine thatdata contained in certain attributes, for example about ten attributesof a total of thousand attributes, is necessary to be present in itsorigination state for the processing to have occurred, and thereforeunlikely to have been modified. In some instances, the identifiedportion of attributes of the technology event record, i.e., the specificattributes, remain the same for all of the technology event records,while in other instances, the portion may vary from one originationtechnology event record (and its counterpart processed records) toanother. As discussed earlier, this metadata is indexed in the eventindex memory location 282 along with the unique processing eventidentifier, for each captured event record (either origination orprocessing record).

Next, the event standardization module 260 typically transforms the eachof the plurality of captured technology event records to a standardformat, as indicated by block 504. This standardization ensures that allof the captured records have the same format, syntax, character set andthe like. In this regard, in some instances the event standardizationmodule 260 transforms/standardizes only the metadata in the records,while in other embodiments, the event standardization module 260transforms/standardizes each of the plurality of attributes for eachcaptured record. Here, the system may match the metadata of a particularprocessed event record, identified at step 425, to the metadata ofidentified origination event records to determine a match.

As illustrated by block 506, the system is then configured to determine,for each of the plurality of standardized technology event records, adigital indicator for the metadata associated with the technology eventrecord. In some embodiments, the digital indicator is a digitalfingerprint that is typically common to the metadata of a particularorigination record and its counterpart processed event record. In someembodiments, the determining the digital indicator comprises producing ahash value for the metadata using a hash function of the charting module265. Typically, a hash value is a fixed length identifier (such as, anumeric value of a fixed length) that uniquely identifies data. Hashvalues often uniquely represent large amounts of data, as much smallernumeric values. In some instances, locality-sensitive hashing (LSH) maybe employed to reduce the dimensionality of the record attributes in themetadata. In other embodiments, the digital indicators comprisechecksums, check digits, randomization functions, and the like. In someinstances, the has values are configured and assigned, globally, over avariety of character encoding systems and character sets such that, thedigital indicators may be matched without requiring datastandardization. For example, a character or string may be assigned asame value for each of its representations in multiple character sets sothat the character or string would have the same digital indicatorirrespective of the format, thereby precluding the data transformationstep at block 504, and hence, further reducing the processing time andmemory requirements.

Next, as illustrated by block 508, the charting module 265, matches theprocessed event record to the associated origination event record basedon at least determining that the digital indicator of the originationevent record matches the digital indicator of the processed eventrecord. For example, after identifying a processed event record at step425, the charting module 265 typically compares the digital indicator ofthe processed event record with the determined digital indicators ofidentified origination event records, to identify a match. Therefore,the charting module 265 is configured to match the event records, in atimely and efficient manner. Furthermore, because the matching isconducted based on the metadata, any modifications to the rest of theattributes would not impact the record mapping/charting.

FIG. 6, illustrates a high level process flow 600 for dynamicallycomparing multi-attribute record data and evaluating the processing ofthe data, at the dynamic event data evaluation application 270. Asillustrated by block 602, the dynamic event data evaluation application270 receives a request or an indication to determine whether a firsttechnology event record was modified during the sequential processing ofthe technology event records by the plurality of technologyapplications. The request or indication typically comprises one or morerecord parameters such as a portion of metadata or data associated withone or more attributes of the first record. In this regard, in someinstances, the request is received from a user 102 via the userapplication 122 of the user device 104. In some instances, the requestis received from an external system such as the entity server 106. Insome instances, the request is received from downstream systems orentities, such as the technology server 105. Here, the technology server105 may transmit the indication, via the network 101, for example, toverify the integrity of the event record retrieved from a transient dataqueue, or when the received event record comprises errors that hinderdownstream processing. In other instances, the indication may bereceived internally from a technology platform application orautomatically triggered by placement of the processed record in thefinal transient queue, to verify the integrity of the processed recordbefore transmitting it to an external entity for further processing,such as the technology server 105.

Next, the dynamic event data evaluation application 270, retrievesmapped logged event metadata and the unique activity identifierassociated with the first record and corresponding mapped records fromthe matching index memory location 284 of the indexing module 280, basedon comparing the received record parameters with the indexed metadata,at block 604. Subsequently, at block 606, and based on the retrievedunique identifier of the first record, the dynamic event data evaluationapplication 270 retrieves the mapped origination event record andprocessed event record from the mapped event data location 294 of theoff-disk storage 290. Here, the retrieved event records comprises eachof the plurality of attributes associated with the records in theirentirety, which were previously transformed to a standard form. Next,the dynamic event data evaluation application 270, compares each of thetechnology attributes of the origination event record to the attributesof the processed event record to determine any modification totechnology attribute data, as indicated by block 608. In the case onidentifying modification in at least one attribute data of the processedevent record, the application may further identify the technologyplatform application, middleware, other components, and/or usersassociated with the modification. In some instances, identifying themodification triggers, automatically, corrective action. In addition, asindicated by block 610, the dynamic event data evaluation application270 is configured to generate, automatically, processing reportsassociated with the comparison results. These reports may comprise thecontent of the retrieved matched records, one or more visual elementssuch as maps, charts and graphs, that are displayed on the user devicedisplay.

As will be appreciated by one of ordinary skill in the art, the presentinvention may be embodied as an apparatus (including, for example, asystem, a machine, a device, a computer program product, and/or thelike), as a method (including, for example, a business process, acomputer-implemented process, and/or the like), or as any combination ofthe foregoing. Accordingly, embodiments of the present invention maytake the form of an entirely software embodiment (including firmware,resident software, micro-code, and the like), an entirely hardwareembodiment, or an embodiment combining software and hardware aspectsthat may generally be referred to herein as a “system.” Furthermore,embodiments of the present invention may take the form of a computerprogram product that includes a computer-readable storage medium havingcomputer-executable program code portions stored therein. As usedherein, a processor may be “configured to” perform a certain function ina variety of ways, including, for example, by having one or morespecial-purpose circuits perform the functions by executing one or morecomputer-executable program code portions embodied in acomputer-readable medium, and/or having one or more application-specificcircuits perform the function.

It will be understood that any suitable computer-readable medium may beutilized. The computer-readable medium may include, but is not limitedto, a non-transitory computer-readable medium, such as a tangibleelectronic, magnetic, optical, infrared, electromagnetic, and/orsemiconductor system, apparatus, and/or device. For example, in someembodiments, the non-transitory computer-readable medium includes atangible medium such as a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), an erasableprogrammable read-only memory (EPROM or Flash memory), a compact discread-only memory (CD-ROM), and/or some other tangible optical and/ormagnetic storage device. In other embodiments of the present invention,however, the computer-readable medium may be transitory, such as apropagation signal including computer-executable program code portionsembodied therein.

It will also be understood that one or more computer-executable programcode portions for carrying out the specialized operations of the presentinvention may be required on the specialized computer includeobject-oriented, scripted, and/or unscripted programming languages, suchas, for example, Java, Perl, Smalltalk, C++, SAS, SQL, Python, ObjectiveC, and/or the like. In some embodiments, the one or morecomputer-executable program code portions for carrying out operations ofembodiments of the present invention are written in conventionalprocedural programming languages, such as the “C” programming languagesand/or similar programming languages. The computer program code mayalternatively or additionally be written in one or more multi-paradigmprogramming languages, such as, for example, F#.

It will further be understood that some embodiments of the presentinvention are described herein with reference to flowchart illustrationsand/or block diagrams of systems, methods, and/or computer programproducts. It will be understood that each block included in theflowchart illustrations and/or block diagrams, and combinations ofblocks included in the flowchart illustrations and/or block diagrams,may be implemented by one or more computer-executable program codeportions.

It will also be understood that the one or more computer-executableprogram code portions may be stored in a transitory or non-transitorycomputer-readable medium (e.g., a memory, and the like) that can directa computer and/or other programmable data processing apparatus tofunction in a particular manner, such that the computer-executableprogram code portions stored in the computer-readable medium produce anarticle of manufacture, including instruction mechanisms which implementthe steps and/or functions specified in the flowchart(s) and/or blockdiagram block(s).

The one or more computer-executable program code portions may also beloaded onto a computer and/or other programmable data processingapparatus to cause a series of operational steps to be performed on thecomputer and/or other programmable apparatus. In some embodiments, thisproduces a computer-implemented process such that the one or morecomputer-executable program code portions which execute on the computerand/or other programmable apparatus provide operational steps toimplement the steps specified in the flowchart(s) and/or the functionsspecified in the block diagram block(s). Alternatively,computer-implemented steps may be combined with operator and/orhuman-implemented steps in order to carry out an embodiment of thepresent invention.

While certain exemplary embodiments have been described and shown in theaccompanying drawings, it is to be understood that such embodiments aremerely illustrative of, and not restrictive on, the broad invention, andthat this invention not be limited to the specific constructions andarrangements shown and described, since various other changes,combinations, omissions, modifications and substitutions, in addition tothose set forth in the above paragraphs, are possible. Those skilled inthe art will appreciate that various adaptations and modifications ofthe just described embodiments can be configured without departing fromthe scope and spirit of the invention. Therefore, it is to be understoodthat, within the scope of the appended claims, the invention may bepracticed other than as specifically described herein.

INCORPORATION BY REFERENCE

To supplement the present disclosure, this application furtherincorporates entirely by reference the following commonly assignedpatent applications:

U.S. Patent Application Docket Number Ser. No. Title Filed On7411US1.014033.2884 15/288,779 REAL TIME EVENT CAPTURE Oct. 7, 2016 nowpublished as AND TRANSFORMATION OF U.S. patent application No. TRANSIENTDATA FOR AN 2018/0101585 INFORMATION NETWORK 7412US1.014033.288515/288,818 REAL TIME EVENT CAPTURE Oct. 7, 2016 now published as ANDANALYSIS OF TRANSIENT U.S. patent application No. DATA FOR ANINFORMATION 2018/0102935 NETWORK

1. A system for real time event capture and transformation of temporarydata for an information network, wherein the system is configured toenable technology event data transformation, processing evaluation anddata mapping, the system comprising: a plurality of technology platformapplications comprising a first application associated with a firsttemporary memory location and a second application associated with asecond temporary memory location; a first proctor module application inoperative communication with the first temporary memory location; asecond proctor module application in operative communication with thesecond temporary memory location; at least one memory device withcomputer-readable program code stored thereon; at least onecommunication device; at least one processing device operatively coupledto the plurality of technology platform applications, the first proctormodule application and the second proctor module application, the atleast one memory device and the at least one communication device,wherein executing the computer-readable code is configured to cause theat least one processing device to: position, by the first application, afirst technology event record associated with a resource transferactivity on a first temporary data queue at the first temporary memorylocation, wherein the first temporary data queue is configured totemporarily store the first technology event record until the firsttechnology event record is retrieved by the second application; capture,by the first proctor module application, the first technology eventrecord, wherein positioning the first technology event record on thefirst temporary data queue is configured to trigger, automatically, thecapture of the first technology event record by the first proctor moduleapplication, wherein the first proctor module application is configuredto capture, in real time, temporary data stored in the first temporarymemory location before the data is retrieved by the second application,wherein capturing further comprises adding the captured first technologyevent record to a first proctor queue; retrieve, by the secondapplication, the first technology event record from the first temporarydata queue at the first temporary memory location; process, at thesecond application, the first technology event record, turning the firsttechnology event record to a first processed technology event record;position, by the second application, the first processed technologyevent record on a second temporary data queue at the second temporarymemory location, wherein the second temporary data queue is configuredto temporarily store the first processed technology event record;capture, by the second proctor module application, the first processedtechnology event record, wherein positioning the processed technologyevent record on the second temporary data queue is configured totrigger, automatically, the capture of the processed technology eventrecord by the second proctor module application, wherein capturingfurther comprises adding the captured first processed technology eventrecord to a second proctor queue; and map, the captured first technologyevent record to the captured first processed technology event record. 2.The system of claim 1, wherein executing the computer-readable code isconfigured to further cause the at least one processing device to:compare the captured first technology event record to the captured firstprocessed technology event record to identify any modification to thefirst technology event record; transmit the first processed technologyevent record to a data integrity checking application of the pluralityof technology platform applications based on determining that the firsttechnology event record has not been modified; and initiate the resourcetransfer activity based on receiving an indication of successfulintegrity check of the first processed technology event record, from thedata integrity checking application.
 3. The system of claim 1, whereinthe first technology event record comprises a plurality of technologyattributes associated with the resource transfer activity, whereinexecuting the computer-readable code is configured to further cause theat least one processing device to: retrieve, by a technology datalogging application, a plurality of captured event records comprisingthe captured first technology event record and the captured firstprocessed technology event record, from the first proctor queue and thesecond proctor queue; assign, at the technology data loggingapplication, a first unique processing event identifier to the capturedfirst technology event record and a second unique processing eventidentifier to the captured first processed technology event record; log,by the technology data logging application, the assigned first uniqueprocessing event identifier and origination event metadata comprising apredetermined portion of the plurality of technology attributesassociated with the captured first technology event record, to a firstevent index memory location of an indexing module; and log, by thetechnology data logging application, the assigned second uniqueprocessing event identifier and processed event metadata comprising thepredetermined portion of the plurality of technology attributesassociated with the captured first processed technology event record, toa second event index memory location of the indexing module.
 4. Thesystem of claim 3, wherein executing the computer-readable code isconfigured to further cause the at least one processing device to: writeeach of the plurality of captured event records comprising the pluralityof technology attributes to a native format event data location of anoff-disk storage, in native format of the captured event record; andwherein the off-disk storage comprises a virtual tape.
 5. The system ofclaim 3, wherein executing the computer-readable code is configured tofurther cause the at least one processing device to transform theplurality of technology attributes associated with each of the pluralityof captured event records to a standard format, using an eventstandardization module.
 6. The system of claim 1, wherein the firsttechnology event record comprises a plurality of technology attributesassociated with the resource transfer activity, wherein mapping thecaptured first technology event record to the captured first processedtechnology event record further comprises: determining, for each of aplurality of captured event records comprising the first technologyevent record and the captured first processed technology event record, aprocessing event type, wherein the processing event type comprises anorigination event record type and a processed event record type; basedon determining that the captured first technology event record is theorigination event record type, assigning a unique activity identifier tothe captured first technology event record; based on determining thatthe captured first processing technology event record is the processedevent record type, matching the captured first processed technologyevent record to the captured first technology event record, whereinmapping further comprises assigning the unique activity identifier ofthe mapped first technology event record to the first processedtechnology event record; and logging, event metadata and the uniqueactivity identifier associated with the mapped first technology eventrecord and the first processed technology event record to a matchingindex memory location of an indexing module; wherein the event metadataassociated with the captured first technology event record comprises apredetermined portion of the plurality of technology attributes of thecaptured first technology event record; wherein the event metadataassociated with the captured first processing technology event recordcomprises the predetermined portion of the plurality of technologyattributes of the captured first processing technology event record. 7.The system of claim 6, wherein executing the computer-readable code isconfigured to further cause the at least one processing device to: writeeach of the mapped first technology event record and the first processedtechnology event record comprising the plurality of technologyattributes to a mapped event data location of an off-disk storage;wherein the off-disk storage comprises a virtual tape.
 8. The system ofclaim 6, wherein the predetermined portion of the plurality oftechnology attributes of the captured first technology event recordcomprises a predetermined portion of the plurality of technologyattributes that are least likely to be modified during the processing ofthe technology event records by the second application.
 9. The system ofclaim 6, wherein mapping the captured first technology event record tothe captured first processed technology event record further comprises:creating a standardized first technology event record by transforming,the plurality of technology attributes associated with the capturedfirst technology event record, to a standard format using an eventstandardization module; creating a standardized first processedtechnology event record by transforming, the plurality of technologyattributes associated with the captured first processed technology eventrecord, to the standard format using the event standardization module;determining, for each of a plurality of standardized technology eventrecords comprising the standardized first technology event record andthe standardized first processed technology event record, the eventmetadata comprising the predetermined first portion of the plurality oftechnology attributes; determining, for each of the plurality ofstandardized technology event records, a digital indicator for the eventmetadata associated with the technology event record; and matching thestandardized first technology event record to the standardized firstprocessed technology event record based on at least determining that thedigital indicator of the standardized first technology event recordmatches the digital indicator of the standardized first processedtechnology event record.
 10. The system of claim 9, wherein determiningthe digital indicator for the event metadata comprises producing hashvalues of the event metadata using a hash function.
 11. A computerprogram product for real time event capture and transformation oftemporary data for an information network, wherein the computer programproduct is configured to enable technology event data transformation,processing evaluation and data mapping, the computer program productcomprising a non-transitory computer-readable storage medium havingcomputer-executable instructions to: position, by a first application, afirst technology event record associated with a resource transferactivity on a first temporary data queue at a first temporary memorylocation, wherein the first temporary data queue is configured totemporarily store the first technology event record until the firsttechnology event record is retrieved by a second application; capture,by a first proctor module application in operative communication withthe first temporary memory location, the first technology event record,wherein positioning the first technology event record on the firsttemporary data queue is configured to trigger, automatically, thecapture of the first technology event record by the first proctor moduleapplication, wherein the first proctor module application is configuredto capture, in real time, temporary data stored in the first temporarymemory location before the data is retrieved by the second application,wherein capturing further comprises adding the captured first technologyevent record to a first proctor queue; retrieve, by the secondapplication, the first technology event record from the first temporarydata queue at the first temporary memory location; process, at thesecond application, the first technology event record, turning the firsttechnology event record to a first processed technology event record;position, by the second application, the first processed technologyevent record on a second temporary data queue at a second temporarymemory location, wherein the second temporary data queue is configuredto temporarily store the first processed technology event record;capture, by a second proctor module application in operativecommunication with the second temporary memory location, the firstprocessed technology event record, wherein positioning the processedtechnology event record on the second temporary data queue is configuredto trigger, automatically, the capture of the processed technology eventrecord by the second proctor module application, wherein capturingfurther comprises adding the captured first processed technology eventrecord to a second proctor queue; and map, the captured first technologyevent record to the captured first processed technology event record.12. The computer program product of claim 11, wherein the non-transitorycomputer-readable storage medium further comprises computer-executableinstructions to: compare the captured first technology event record tothe captured first processed technology event record to identify anymodification to the first technology event record; transmit the firstprocessed technology event record to a data integrity checkingapplication of the plurality of technology platform applications basedon determining that the first technology event record has not beenmodified; and initiate the resource transfer activity based on receivingan indication of successful integrity check of the first processedtechnology event record, from the data integrity checking application.13. The computer program product of claim 11, wherein the firsttechnology event record comprises a plurality of technology attributesassociated with the resource transfer activity, wherein mapping thecaptured first technology event record to the captured first processedtechnology event record further comprises: determining, for each of aplurality of captured event records comprising the first technologyevent record and the captured first processed technology event record, aprocessing event type, wherein the processing event type comprises anorigination event record type and a processed event record type; basedon determining that the captured first technology event record is theorigination event record type, assigning a unique activity identifier tothe captured first technology event record; based on determining thatthe captured first processing technology event record is the processedevent record type, matching the captured first processed technologyevent record to the captured first technology event record, whereinmapping further comprises assigning the unique activity identifier ofthe mapped first technology event record to the first processedtechnology event record; and logging, event metadata and the uniqueactivity identifier associated with the mapped first technology eventrecord and the first processed technology event record to a matchingindex memory location of an indexing module; wherein the event metadataassociated with the captured first technology event record comprises apredetermined portion of the plurality of technology attributes of thecaptured first technology event record; wherein the event metadataassociated with the captured first processing technology event recordcomprises the predetermined portion of the plurality of technologyattributes of the captured first processing technology event record. 14.The computer program product of claim 13, wherein the non-transitorycomputer-readable storage medium further comprises computer-executableinstructions to: write each of the mapped first technology event recordand the first processed technology event record comprising the pluralityof technology attributes to a mapped event data location of an off-diskstorage; wherein the off-disk storage comprises a virtual tape.
 15. Thecomputer program product of claim 13, wherein mapping the captured firsttechnology event record to the captured first processed technology eventrecord further comprises: creating a standardized first technology eventrecord by transforming, the plurality of technology attributesassociated with the captured first technology event record, to astandard format using an event standardization module; creating astandardized first processed technology event record by transforming,the plurality of technology attributes associated with the capturedfirst processed technology event record, to the standard format usingthe event standardization module; determining, for each of a pluralityof standardized technology event records comprising the standardizedfirst technology event record and the standardized first processedtechnology event record, the event metadata comprising the predeterminedfirst portion of the plurality of technology attributes; determining,for each of the plurality of standardized technology event records, adigital indicator for the event metadata associated with the technologyevent record; and matching the standardized first technology eventrecord to the standardized first processed technology event record basedon at least determining that the digital indicator of the standardizedfirst origination event record matches the digital indicator of thestandardized first processed technology event record.
 16. The computerprogram product of claim 15, wherein determining the digital indicatorfor the event metadata comprises producing hash values of the eventmetadata using a hash function.
 17. A computer implemented method forreal time event capture and transformation of temporary data for aninformation network, wherein the computer implemented method isconfigured to enable technology event data transformation, processingevaluation and data mapping, the computer implemented method comprising:positioning, by a first application, a first technology event recordassociated with a resource transfer activity on a first temporary dataqueue at a first temporary memory location, wherein the first temporarydata queue is configured to temporarily store the first technology eventrecord until the first technology event record is retrieved by a secondapplication; capturing, by a first proctor module application inoperative communication with the first temporary memory location, thefirst technology event record, wherein positioning the first technologyevent record on the first temporary data queue is configured to trigger,automatically, the capture of the first technology event record by thefirst proctor module application, wherein the first proctor moduleapplication is configured to capture, in real time, temporary datastored in the first temporary memory location before the data isretrieved by the second application, wherein capturing further comprisesadding the captured first technology event record to a first proctorqueue; retrieving, by the second application, the first technology eventrecord from the first temporary data queue at the first temporary memorylocation; processing, at the second application, the first technologyevent record, turning the first technology event record to a firstprocessed technology event record; positioning, by the secondapplication, the first processed technology event record on a secondtemporary data queue at a second temporary memory location, wherein thesecond temporary data queue is configured to temporarily store the firstprocessed technology event record; capturing, by a second proctor moduleapplication in operative communication with the second temporary memorylocation, the first processed technology event record, whereinpositioning the processed technology event record on the secondtemporary data queue is configured to trigger, automatically, thecapture of the processed technology event record by the second proctormodule application, wherein capturing further comprises adding thecaptured first processed technology event record to a second proctorqueue; and mapping, the captured first technology event record to thecaptured first processed technology event record.
 18. The computerimplemented method of claim 17, wherein the computer implemented methodfurther comprises: comparing the captured first technology event recordto the captured first processed technology event record to identify anymodification to the first technology event record; transmitting thefirst processed technology event record to a data integrity checkingapplication of the plurality of technology platform applications basedon determining that the first technology event record has not beenmodified; and initiating the resource transfer activity based onreceiving an indication of successful integrity check of the firstprocessed technology event record, from the data integrity checkingapplication.
 19. The computer implemented method of claim 17, whereinthe first technology event record comprises a plurality of technologyattributes associated with the resource transfer activity, wherein thecomputer implemented method further comprises: determining, for each ofa plurality of captured event records comprising the first technologyevent record and the captured first processed technology event record, aprocessing event type, wherein the processing event type comprises anorigination event record type and a processed event record type; basedon determining that the captured first technology event record is theorigination event record type, assigning a unique activity identifier tothe captured first technology event record; based on determining thatthe captured first processing technology event record is the processedevent record type, matching the captured first processed technologyevent record to the captured first technology event record, whereinmapping further comprises assigning the unique activity identifier ofthe mapped first technology event record to the first processedtechnology event record; and logging, event metadata and the uniqueactivity identifier associated with the mapped first technology eventrecord and the first processed technology event record to a matchingindex memory location of an indexing module; wherein the event metadataassociated with the captured first technology event record comprises apredetermined portion of the plurality of technology attributes of thecaptured first technology event record; wherein the event metadataassociated with the captured first processing technology event recordcomprises the predetermined portion of the plurality of technologyattributes of the captured first processing technology event record. 20.The computer implemented method of claim 19, wherein mapping thecaptured first technology event record to the captured first processedtechnology event record further comprises: creating a standardized firsttechnology event record by transforming, the plurality of technologyattributes associated with the captured first technology event record,to a standard format using an event standardization module; creating astandardized first processed technology event record by transforming,the plurality of technology attributes associated with the capturedfirst processed technology event record, to the standard format usingthe event standardization module; determining, for each of a pluralityof standardized technology event records comprising the standardizedfirst technology event record and the standardized first processedtechnology event record, the event metadata comprising the predeterminedfirst portion of the plurality of technology attributes; determining,for each of the plurality of standardized technology event records, adigital indicator for the event metadata associated with the technologyevent record; and matching the standardized first technology eventrecord to the standardized first processed technology event record basedon at least determining that the digital indicator of the standardizedfirst origination event record matches the digital indicator of thestandardized first processed technology event record.